-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: Xfails on Python 3.10 #41595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Xfails on Python 3.10 #41595
Conversation
right this was done on purpose so that we have time to fix the tests so happy to merge this once all green otherwise |
@jreback I think we should xfail these instead of doing this for now, and look into fixing them. The current setup means that its hard to tell if something breaks more tests on Python 3.10 in addition to the ones currently failing. |
sure happy to do that as well. I agree that's better. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good ;
comment and ping when green
Hello @lithomas1! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-06-28 15:35:29 UTC |
Still WIP becaue there's a ton of flaky tests and idk what's wrong with sparse tests. |
thanks @lithomas1 very nice! |
@meeseeksdev backport 1.3.x |
Something went wrong ... Please have a look at my logs. |
Co-authored-by: Thomas Li <[email protected]>
The Python 3.10 CI is actually red, but the continue-on-error flag makes it so that the job is not failed. WIP because tests actually have to be fixed.Added Xfails for some tests. Pretty much green except for #41935